Skip to content

ci(windows): Authenticode-sign releases through Azure Artifact Signing - #160

Merged
danielss-dev merged 1 commit into
mainfrom
ci/windows-artifact-signing
Nov 11, 2026
Merged

danielss-dev merged 1 commit into
mainfrom
ci/windows-artifact-signing

Conversation

@danielss-dev

Copy link
Copy Markdown
Owner

Authenticode-signs the Windows release through Azure Artifact Signing (shared account halterio-signing, profile public-trust).

Signs strand.exe and the MSI (Tauri sign command), strand-cli.exe (bundled as a resource, so signed in build-companion.mjs), and the separately downloaded strand-azdo.exe helper before it is archived and hashed. The helper is built in its own step, so its dependency build scripts never see the credentials. check-release-security.mjs now requires this wiring; docs/packaging.md documents it. The Store MSIX route is unchanged.

  • scripts/windows-signing-client.ps1: fetches Microsoft.ArtifactSigning.Client 1.0.128 (SHA-256 pinned), writes the account metadata, and writes a Tauri config setting bundle.windows.signCommand to scripts/windows-sign.ps1, passed to tauri-action as --config.
  • scripts/windows-sign.ps1: newest Windows SDK SignTool + the dlib + Microsoft's timestamp server, then fails unless Get-AuthenticodeSignature is Valid.
  • Verify step: the installers, plus every .exe the MSI installs (administrative install unpack), must have valid signatures.
  • Gated on the repo variable WINDOWS_SIGNING == 'true', which isn't set: until the certificate profile exists (identity validation pending in Azure), releases build exactly as before.
  • Credentials: service principal strand-release-signing with only the Certificate Profile Signer role; secrets AZURE_SIGNING_CLIENT_ID / AZURE_SIGNING_TENANT_ID / AZURE_SIGNING_CLIENT_SECRET are already set (expire 2028-11-11).

Not run on Windows yet: the PowerShell parses cleanly and actionlint passes; pnpm release:check-security passes.

🤖 Generated with Claude Code

Tauri signs the app exe and installers through scripts/windows-sign.ps1
(bundle.windows.signCommand from a CI-written --config), and a verify
step checks the installers and every exe the MSI installs. Off until the
repository variable WINDOWS_SIGNING is true.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@danielss-dev
danielss-dev merged commit 2e5bff9 into main Nov 11, 2026
9 of 10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant